Ping fails and tracert times out (doubt telnet would work either then): C:\Users\me>tracert 205.203.131.130 Tracing route to mx.marketwatchmail.com [205.203.131.130] over a maximum of 30 hops: [... edited out] 7 415 ms 428 ms 454 ms ae-0-0.pr0.nyc30.tbone.rr.com [66.109.6.159] 8 447 ms 419 ms 479 ms xe-7-2-0.edge2.newark1.level3.net [4.59.20.33] 9 439 ms 431 ms 427 ms dow-jones-c.edge2.newark1.level3.net [4.59.20.254] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. [...] Email working OK otherwise. Even Blackberry phones seem "back in business".

On Thu, 13 Oct 2011 12:47:54 +0000, Le Pivert wrote: >Ping fails and tracert times out (doubt telnet would work either then): The ICMP is not accepted beyond the firewall at 4.59.20.254. You're outside your network so you have no control over that. [ snip ] >Email working OK otherwise. So you're able to deliver email to domain now? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Le, How about the issue, any updates? If the issue persists, please explain your test result in detail. Thanks, Evan

None of those entries in the SMTP Send Connector log yesterday or today. Perhaps it's fixed on the other end?

Hello all, I've noticed that for the last couple days, but much less today , my SMTP Send Connector log contains many of these entries (below). We don't even make it to HELO or EHLO. Is the server down at the other end? Is something wrong on my end? For the most part, we can send mail although some users have mentioned that their recipient never received it. That's what led me to look at Message Tracking Logs and the Protocol Log (SMTP Send). 2011-10-12T00:01:20.440Z,OUTBOUND,08CE5569A05578B6,0,,205.203.131.130:25,*,,attempting to connect 2011-10-12T00:01:41.454Z,OUTBOUND,08CE5569A05578B6,1,,205.203.131.130:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.130:25" 2011-10-12T00:01:41.454Z,OUTBOUND,08CE5569A05578B6,0,,205.203.131.128:25,*,,attempting to connect 2011-10-12T00:02:02.467Z,OUTBOUND,08CE5569A05578B6,1,,205.203.131.128:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.128:25" 2011-10-12T00:12:08.254Z,OUTBOUND,08CE5569A05578C4,0,,205.203.131.130:25,*,,attempting to connect 2011-10-12T00:12:29.252Z,OUTBOUND,08CE5569A05578C4,1,,205.203.131.130:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.130:25" 2011-10-12T00:12:29.252Z,OUTBOUND,08CE5569A05578C4,0,,205.203.131.128:25,*,,attempting to connect 2011-10-12T00:12:50.281Z,OUTBOUND,08CE5569A05578C4,1,,205.203.131.128:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.128:25" 2011-10-12T00:22:51.216Z,OUTBOUND,08CE5569A05578CC,0,,205.203.131.130:25,*,,attempting to connect 2011-10-12T00:23:12.230Z,OUTBOUND,08CE5569A05578CC,1,,205.203.131.130:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.130:25" 2011-10-12T00:23:12.230Z,OUTBOUND,08CE5569A05578CC,0,,205.203.131.128:25,*,,attempting to connect 2011-10-12T00:23:33.228Z,OUTBOUND,08CE5569A05578CC,1,,205.203.131.128:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.128:25" 2011-10-12T00:33:38.846Z,OUTBOUND,08CE5569A05578D5,0,,205.203.131.128:25,*,,attempting to connect 2011-10-12T00:33:59.860Z,OUTBOUND,08CE5569A05578D5,1,,205.203.131.128:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.128:25" 2011-10-12T00:33:59.860Z,OUTBOUND,08CE5569A05578D5,0,,205.203.131.130:25,*,,attempting to connect 2011-10-12T00:34:20.889Z,OUTBOUND,08CE5569A05578D5,1,,205.203.131.130:25,*,,"Failed to connect. Error Code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.203.131.130:25" 2011-10-12T00:36:19.248Z,OUTBOUND,08CE5569A05578D9,0,,143.69.251.34:25,*,,attempting to connect

Otherwise = meaning no one has mentioned any problems - except one, probably unrelated, where some recipients do not receive messages when the sender sends them from Outlook - but they do when sent from OWA. Three consistent results in a row. But besides that problem, email seems to be working fine for our users. Otherwise = also meaning that I did not see those lines in yesterdays logs as much as before.

Evan, There are still these entries in the SMTP Send Connector log. If do not know if they are serious and at any rate, they seem to be due to something outside our network. The vast majority of our users are able to send email - and receive responses to these emails. As for my ping and tracert tests, I am not sure what I could clarify? ---------------- Possible reason??? Could it simply be that there were mail servers out there that were decommissioned but someone forgot to update DNS records???

None of those entries in the SMTP Send Connector log yesterday or today. Perhaps it's fixed on the other end?

On Wed, 12 Oct 2011 12:50:33 +0000, Le Pivert wrote: >I've noticed that for the last couple days, but much less today , my SMTP Send Connector log contains many of these entries (below). > >We don't even make it to HELO or EHLO. > >Is the server down at the other end? Is something wrong on my end? Have you tried these yet? ping 205.203.131.130 telnet 205.203.131.130 25 tracert 205.203.131.130 That's pretty basic stuff to start your investigation. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP